Fix: #69
Fix: #96

Builds on: #127

Opening as an early draft just to track progress.

currently at a point where the iterators exhaust and prematurely close the runner

• Separate start/stop and init/deinit - have intermediate state whre nodes stay inited but aren't actively running. also need to keep scheduler and store after failures, so probably move clearing those to the init method.
• iter method to iterate through results
• run method with unlimited n
• run method with fixed n
• run method with iter
• test store clearing on all nodes
• figure out why zmqrunner command node can escape pytest stdout capture

Along the way we resolved a few other things

• Figured out that one source of the zmq thread/async deadlock might be threading locks held within the logging modules when the processes are forked, so ensured that loggers in child processes create their own file and stdout loggers. this ends up being much cleaner than the prior implementation, where we not have one logging file per process rather than one per process per logger, which created an ungodly spray of log files
• along the same lines, we also added a 'ping' loop to the zmq startup, where sometimes (esp on mac in the github runner) the nodes are slow to start listening to events in pub/sub sockets. this loop prompts them to re-identify themselves, which then sends additional announce messages, which then causes them to update their states, which then appropriately releases the "ready" lock in the command node.
• this let us turn off debug logging by default in testing, which was a weird crutch that kept things running on mac in the CI runners...

📚 Documentation preview 📚: https://noob--129.org.readthedocs.build/en/129/